Skip to content

Conversation

@robinborst95
Copy link
Contributor

Reason

In our application we allow changing filters that are passed to the infinity model, so we create a new infinity model. However, when the current model has reached infinity, updating the infinity model does not update within the infinity loader, so the new model does not load more pages.

I added a test that reflects this, and fixed it by adding an empty div when not shown, to host the {{did-update}}. Not an ideal solution, so let me know if there are other solutions 👍

Copy link
Contributor

@MelSumner MelSumner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know what else to suggest but I can at least help you get unblocked with this workaround if that's useful.

Adding for clarity: obviously we don't want to use {{did-update}} but it's already being used in this addon, so there's no sense in keeping you blocked while the addon is updated. I'm going to file an issue so this addon can be evaluated for further updates or maintenance.

@MelSumner MelSumner merged commit ab94e9a into adopted-ember-addons:main Apr 29, 2025
14 checks passed
@github-actions github-actions bot mentioned this pull request Apr 29, 2025
@robinborst95 robinborst95 deleted the fix/infinity-loader-model-changed branch April 29, 2025 12:54
@MelSumner MelSumner added the bug label Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants